Application of brokering methods to scalability characteristics

ABSTRACT

This application describes an application of resource unit brokering algorithms, chip management methods for automated brokering, chip management methods for live brokering, and chip allocation methods to the brokering of scalability characteristics of service level management within an enterprise. Typically, the scalability characteristics are derived from known capacity values that are provided by configuration managers. Calculations are made on the capacity values and maximum quantities of the availability resource units are provided to resource brokers for spot or periodic sale and auction to one or more buyer&#39;s agents.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is related in some aspects to commonly owned patent application Ser. No. (to be provided), entitled “RESOURCE MANAGEMENT FRAMEWORK”, assigned attorney docket number END920060217US1, filed concurrently herewith, the entire contents of which are herein incorporated by reference.

This application is related in some aspects to commonly owned patent application number (to be provided), entitled “METHOD, SYSTEM, AND PROGRAM PRODUCT FOR SELECTING A BROKERING METHOD FOR OBTAINING DESIRED SERVICE LEVEL CHARACTERISTICS”, assigned attorney docket number END920060218US1, filed concurrently herewith, the entire contents of which are herein incorporated by reference.

This application is related in some aspects to commonly owned patent application number (to be provided), entitled “NON-DEPLETING CHIPS FOR OBTAINING DESIRED SERVICE LEVEL CHARACTERISTICS”, assigned attorney docket number END920060219US1, filed concurrently herewith, the entire contents of which are herein incorporated by reference.

This application is related in some aspects to commonly owned patent application number (to be provided), entitled “DISCRETE, DEPLETING CHIPS FOR OBTAINING DESIRED SERVICE LEVEL CHARACTERISTICS”, assigned attorney docket number END920060220US1, filed concurrently herewith, the entire contents of which are herein incorporated by reference.

This application is related in some aspects to commonly owned patent application number (to be provided), entitled “FLUID, DEPLETING CHIPS FOR OBTAINING DESIRED SERVICE LEVEL CHARACTERISTICS”, assigned attorney docket number END920060221US1, filed concurrently herewith, the entire contents of which are herein incorporated by reference.

This application is related in some aspects to commonly owned patent application number (to be provided), entitled “APPLICATION OF BROKERING METHODS TO AVAILABILITY CHARACTERISTICS”, assigned attorney docket number END920060224US1, filed concurrently herewith, the entire contents of which are herein incorporated by reference.

This application is related in some aspects to commonly owned patent application number (to be provided), entitled “APPLICATION OF BROKERING METHODS TO PERFORMANCE CHARACTERISTICS”, assigned attorney docket number END920060225US1, filed concurrently herewith, the entire contents of which are herein incorporated by reference.

This application is related in some aspects to commonly owned patent application number (to be provided), entitled “APPLICATION OF BROKERING METHODS TO RECOVERABILITY CHARACTERISTICS”, assigned attorney docket number END920060226US1, filed concurrently herewith, the entire contents of which are herein incorporated by reference.

This application is related in some aspects to commonly owned patent application number (to be provided), entitled “APPLICATION OF BROKERING METHODS TO SECURITY CHARACTERISTICS”, assigned attorney docket number END920060227US1, filed concurrently herewith, the entire contents of which are herein incorporated by reference.

This application is related in some aspects to commonly owned patent application number (to be provided), entitled “APPLICATION OF BROKERING METHODS TO OPERATIONAL SUPPORT CHARACTERISTICS”, assigned attorney docket number END920060229US1, filed concurrently herewith, the entire contents of which are herein incorporated by reference.

FIELD OF THE INVENTION

The present invention generally relates to the brokering of scalability characteristics. Specifically, the present invention relates to the application of brokering methods and chip allocation/management methods to brokering scalability characteristics.

BACKGROUND OF THE INVENTION

Businesses are experiencing an ever-increasing trend to achieve higher utilization of computing resources. Companies that provide their own IT computing services are being driven to find ways to decrease costs by increasing utilization. Moreover, companies that provide these services are being driven to reduce overhead and become more competitive by increasing utilization of these resources. Numerous studies over the past decade have shown that typical utilization levels of computing resources within service delivery centers, raised floors, and data centers fall between 20% and 80%. This leaves a tremendous amount of white space with which to improve utilization and drive costs down.

These issues are compounded by the fact that, in many instances, multiple parties compete for common resources. Such competition can occur both on an inter-organization level as well as on an intra-organization level (e.g., between business units). To this extent, none of the existing approaches address how many resources a particular party is allowed to consume. That is, none of the existing approaches provide a way to adequately ration a party the computational resources in a way that will fulfill its needs, while not preventing the needs of other parties from being met. Accordingly, there exists a need in the art to overcome the deficiencies and limitations described hereinabove.

SUMMARY OF THE INVENTION

Aspects of this application describe the application of resource unit brokering algorithms, chip management methods for automated brokering, chip management methods for live brokering, and chip allocation methods to the brokering of scalability characteristics of service level management within an enterprise. Typically, the scalability characteristics are derived from known capacity values that are provided by configuration managers. Calculations are made on the capacity values and maximum quantities of the availability resource units are provided to resource brokers for spot or periodic sale and auction to one or more buyer's agents. Among other things, this application describes an offering of scalability service level characteristics for sale or auction in a Service Level and IT Resource Optimization framework.

One aspect of the present invention provides a method for applying brokering methods to scalability characteristics, comprising: obtaining configuration information; translating the configuration information that pertains to a scalability service category into a quantity of resource units; dividing the quantity of resource units by an associated cost for each of a set of service levels; determining a maximum quantity of each of the set of service levels that can be allocated for the quantity of resource units; and generating a matrix of possible configurations.

Another aspect of the present invention provides a system for applying brokering methods to scalability characteristics, comprising: a system for obtaining configuration information; a system for translating the configuration information that pertains to a scalability service category into a quantity of resource units; a system for dividing the quantity of resource units by an associated cost for each of a set of service levels; a system for determining a maximum quantity of each of the set of service levels that can be allocated for the quantity of resource units; and a system for generating a matrix of possible configurations.

Another aspect of the present invention provides a program product stored on a computer readable medium for applying brokering methods to scalability characteristics, the computer readable medium comprising program code for causing a computer system to: obtain configuration information; translate the configuration information that pertains to a scalability service category into a quantity of resource units; divide the quantity of resource units by an associated cost for each of a set of service levels; determine a maximum quantity of each of the set of service levels that can be allocated for the quantity of resource units; and generate a matrix of possible configurations.

Another aspect of the present invention provides computer software embodied in a propagated signal for applying brokering methods to scalability characteristics, the computer software comprising instructions for causing a computer system to: obtain configuration information; translate the configuration information that pertains to a scalability service category into a quantity of resource units; divide the quantity of resource units by an associated cost for each of a set of service levels; determine a maximum quantity of each of the set of service levels that can be allocated for the quantity of resource units; and generate a matrix of possible configurations.

Another aspect of the present invention provides a method for deploying a system for applying brokering methods to scalability characteristics, comprising: providing a computer infrastructure being operable to: obtain configuration information; translate the configuration information that pertains to a scalability service category into a quantity of resource units; divide the quantity of resource units by an associated cost for each of a set of service levels; determine a maximum quantity of each of the set of service levels that can be allocated for the quantity of resource units; and generate a matrix of possible configurations.

Another aspect of the present invention provides a data processing system for applying brokering methods to scalability characteristics, comprising: a processing unit, a bus coupled to the processing unit, a memory medium coupled to the bus, the bus comprising instructions, which when executed by the processing unit causes the data processing system to: obtain configuration information; translate the configuration information that pertains to a scalability service category into a quantity of resource units; divide the quantity of resource units by an associated cost for each of a set of service levels; determine a maximum quantity of each of the set of service levels that can be allocated for the quantity of resource units; and generate a matrix of possible configurations.

Each of these aspects can also include one or more of the following features (among others): using the matrix in an auction of computer resources; determining a winner of the auction; applying a multiplier to a bid of chips submitted by the winner to yield an adjusted amount of chips; deducting the adjusted amount of chips from a quantity of chips allocated to the winner; the bid being submitted to a resource unit broker by an agent on behalf of a party, and the bid being one a plurality of bids submitted by at least one agent on behalf of a plurality of parties; and the matrix being provided to the resource unit broker.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other features of this invention will be more readily understood from the following detailed description of the various aspects of the invention taken in conjunction with the accompanying drawings in which:

FIG. 1 shows an illustrative resource management framework according to the present invention.

FIG. 2 depicts a method flow diagram according to the present invention.

FIG. 3 shows a more detailed computerized implementation of the present invention.

The drawings are not necessarily to scale. The drawings are merely schematic representations, not intended to portray specific parameters of the invention. The drawings are intended to depict only typical embodiments of the invention, and therefore should not be considered as limiting the scope of the invention. In the drawings, like numbering represents like elements.

DETAILED DESCRIPTION OF THE INVENTION

For convenience, the Detailed Description of the Invention has the following sections:

I. General Description

II. Computerized Implementation

I. General Description

As used herein, the following terms have the following definitions:

“Chip” means any unit (virtual or otherwise) that may be exchanged for resources such as IT resources.

“Party” means any individual, group of individuals, department, business unit, cell of a component business model, etc.

“Discrete Event” means a scheduled event such as an auction.

“Fluid Event” means any non-scheduled event such as a random purchase.

“Service Level Characteristic” means any type of computer or IT requirement needed by the business, including any non-functional requirements that specify criteria that can be used to judge the operation of a system, rather than specific behaviors.

“Elemental Bidding Resource (EBR)” means any computational resource (e.g., memory, processing cycles, etc.) sought by a party to accomplish objectives.

As indicated above, this application describes (among other things) an application of resource unit brokering algorithms, chip management methods for automated brokering, chip management methods for live brokering, and chip allocation methods to the brokering of scalability characteristics of service level management within an enterprise. Typically, the scalability characteristics are derived from known capacity values that are provided by configuration managers. Calculations are made on the capacity values and maximum quantities of the availability resource units are provided to resource brokers for spot or periodic sale and auction to one or more buyers' agents. Among other things, this application describes the offering of scalability service level characteristics for sale or auction in a Service Level and IT Resource Optimization framework.

Each service level category within a service level management framework can be decomposed into numerous component building blocks that tie into the sundry infrastructure categories within the IT infrastructure. These infrastructure categories include the storage subsystems, storage networks, servers or hosts, local area networks, operating systems and applications. It is understood that there might be other infrastructure categories depending upon how the infrastructure components of IT are decomposed.

The existence of certain components or quantities of components in each infrastructure category will predicate the ability to provide a particular service or provide differing service levels of the service. These components can be expressed typically in terms of capacities, assets, personnel and configurations. It is these constituent capacities, assets, personnel and configurations that are grouped and offered to aid in the support of a particular service level. This application does not discuss the groups that comprise a particular service level. Rather, it this application describes the need for these groups and how multiple groups of capacities, assets, personnel and configurations are required to define service levels. The constituent capacities, assets, personnel and configurations each have unique enablers that allow them to fit into the overall Service Level and IT Resource Optimization framework. This application describes (among other things) illustrative methods and processes to take a suggested grouping of constituent capacities, assets, personnel and configurations as they relate to a scalability service category and enable them to be sold, bartered and auctioned in the Service Level and IT Resource Optimization framework being advanced by the inventors.

Referring now to FIG. 1, a resource management framework (hereinafter framework 10) is depicted as described in attorney docket number END920060217US1, which was cross-referenced and incorporated above. This framework is typically leveraged under the present invention, and hence, is being shown and described in conjunction with FIG. 1. As shown, framework 10 is generally comprised of business units 12A-N, buyer's agents 14A-N, resource unit capacity planner 16, resource allocation software 18, optional resource unit change and configuration manager 20, and resource unit broker 28. These components typically leverage additional assets such as chip usage trending 21A-N, requester chip pool 22A-N, and service level and infrastructure category baseline 24.

An objective of framework 10 is to reach a means of maximizing utilization of IT Resources among competing consumers such as business units 12A-B by distribution of the decision making/allocation process according to relative needs of applications. Doing so eliminates the need for traditional service level agreements (SLAs), and allows each business unit 12A-N to make dynamic “free market” decisions as to how best to obtain the service levels required from a highly-commoditized IT service provider.

To this end, business units 12A-N relay their priorities and computing needs to the buyer's agents 14A-N. Buyer's agents 14A-N then determine whether to engage in cooperative or competitive negotiations and implement a request for an EBR on the business unit's 12A-N behalf. Various methods can be employed by the resource unit broker 28 to fulfill requests for resources to consumers or business units 12A-N. One method is using non-depleting chips (as further described in attorney docket number END920060219US1, which was cross-referenced and incorporated above), another involves the use of discrete chips (as further described in attorney docket number END920060220US1, which was cross-referenced and incorporated above). Yet another involves the use of fluid chips (as further described in attorney docket number END920060221US1, which was cross-referenced and incorporated above). Regardless, the buyers' agents 14A-N understand the thresholds business units 12A-N are willing to pay, their associated targets for various service level characteristics, and will programmatically employ the most advantageous bidding strategy.

The resource unit capacity planner 16 reports to resource unit brokers 28 (i.e., auctioneers) what resources are available (e.g., infrastructure components) at any given time. Resource allocation software 18 includes products such as Enterprise Workload manager (EWLM), WebSphere XD, and Partition Load Manager (EWLM, Enterprise Workload Manager, WebSphere XD, and Partition Load Manage are trademarks of IBM Corp. in the United States and/or other countries). The goal-oriented policies within these products are updated by inputs from the resource unit broker 28 and/or resource unit broker capacity 16. Change management may be all self-contained in resource allocation software 18, or there may be cases where additional change control needs to be performed. This functionality is provided herein by optional resource unit change and configuration manager 20.

As indicated above, the present invention involves the management and/or allocation of discrete, depleting chips to parties such as business units 12A-N. That is, business units 12A-N will be allocated a certain/fixed quantity of chips pursuant to a business transaction (e.g., a financial transaction). Those chips can then be used for bidding in an attempt to be allocated computational resources. Under an embodiment of the present invention, the chips are considered discrete because they are intended to be used in a scheduled event such as a scheduled auction. In this regard, auction winners are granted resources for known periods of time, and can thus base future decisions on the knowledge that they are ensured the desired resources for the duration of the allocation cycle.

Consider, for the sake of simplicity, the case where only two business units 12A-N are competing for IT resources. These business units 12A-N will be known simply as BU1 and BU2, and each is represented by its own respective agent 14A-N. In the discrete chip model, again, periodic auctions are held, and winners determined for the duration of the allocation cycle, such that resources are distributed accordingly. Specifically, agents 14A-N will submit bids on behalf of business units 12A-N. Each bid is for an amount (e.g., one or more) of chips that were allocated to business units 12A-N. It should be noted that each business unit 12A-N is not necessarily allocated the same amount of chips. For example, business unit “A” may be able to purchase more chips than business unit “B”. In any event, resource unit broker 28 will act as an auctioneer and determine a winner. As part of its role, resource unit broker 28 will communicate with resource unit capacity planner 16 and resource allocation software 18 as outlined above.

Referring now to FIG. 2, a method flow diagram according to the present invention is shown. Initially, in step S1, current configuration information (CI) is maintained by an external process or system, wherein this CI is passed along. This CI includes capacities, assets, personnel, systems and the like that are arranged into supported configurations to support the IT infrastructure. The particular CI that pertains most to the scalability service category is translated into a resource unit in step S2, which is the most granular unit of asset, personnel, capacity, etc. that can be described. For example, there might exist 80 TBs of usable storage capacity available in the storage infrastructure category that can be provisioned to for new use. The smallest allocatable increment of capacity is 100 GB and is set by IT policy. Therefore, there exists 800 storage capacity resource units. This simple example can be expanded to numbers of physical servers, number of network interface cards (NICs), number of resources required to support incident management processes, etc. In step S3, each resource unit group is further decomposed into a varying level of service based upon the maximum CI information for scalability service level categories by dividing the total CI information for each scalability service level related capacities, assets, personnel and configurations by the elemental biddable resource cost for that supported configuration, where a configuration is a logical collection of capacities, assets and personnel to meet or exceed a service level.

As depicted in step S4, the resource units that comprise the scalability service category generally include (among others) the: high provisioning system priority; medium provisioning system priority; low provisioning system priority, and provisioning system usage. Each resource unit can be grouped into several infrastructure category configurations to form a varying series of service levels, called elemental biddable resources (EBR). The EBR is assigned a simple weight to denote its “cost” or complexity of implementation compared to other EBRs in that particular infrastructure category. The scale can be described by the following:

EBR 1 is the same as a single resource unit,

EBR 2 is approx. double in complexity or cost above EBR 1,

EBR 3 is approx. double in complexity or cost above EBR 2,

EBR 5 is approx. double in complexity or cost above EBR 3.

Note: the quantifiable difference between each entry in the EBR scale is not novel by itself, but it is important to note that there are differences in each entry and that going from the lowest (1 in this example) to the highest (5 in this example) the service levels improve. Additionally, the numbering system is arbitrary, suffice that each entry be unique and lower numbers equate to lower levels of service.

Once the EBR scale is defined for each applicable infrastructure category, a calculation is made in step S5 to determine how much of each resource unit can be allocated to maintain a service level configuration. Once the EBR scale is defined for each applicable infrastructure category, a calculation is made to determine how much of each resource unit can be allocated to maintain a service level configuration. For example, if the CI returns that the provisioning system can handle 100 simultaneous provisioning requests, the calculations made in this step shows that for:

EBR 1: up to 100 (100/1) Non-sev general requests can be managed, but are handled after all severity rated requests;

EBR 2: up to 50 (100/2) Sev 3 low priority requests can be managed, but take low priority after Sev 1 and Sev 2 requests;

EBR 3: up to 33 (100/3) Sev 2 medium priority requests can be managed, but take medium priority after Sev 1 requests; and

EBR 5: up to 20 (100/5) Sev 1 high priority requests can be managed, and take the highest priority on first come first served basis.

A matrix of maximum possible configurations for each EBR scale is provided to the resource unit broker(s) along with a reserve price for each resource unit configuration in the scale in step S6. In step S7, the resource unit broker(s) auction or sell the resource units to the buyer's agents and win results including number of chips used to win the bid are provided back to this process. In making this transaction, any algorithm or theory could be applied (e.g., static event(s), discrete event(s). Regardless, in step S8, a multiplier is applied to the number chips used to win and the adjusted amount is deducted from the chip bank for the winning buyer's agent. This multiplier is based on an EBR scale such as the following:

EBR 1: chips required to win ×1

EBR 2: chips required to win ×2

EBR 3: chips required to win ×3

EBR 5: chips required to win ×5

In an alternate embodiment, this multiplier can used to set the reserve bid for each resource unit configuration available as opposed to a multiplier at the end of the auction process. By adjusting the multiplier, more or less economies of scale can be realized. The inventors also denote that the multiplier need not be static, and in fact, can be adjusted based upon resource unit supply. Regardless, in step S9, those resource unit configurations are placed in a consumed state and updated configuration information is sent to the configuration manager or configuration management process. In step S10, an inquiry request is sent to the winning buyer's agent to provide more details on the nature of provisioning the winning resource unit configuration, such as when to provision the resources and other capacity information as required. In step S11, the resource unit configurations are allocated as requested. The process can then be repeated for each buyer's agent and/or for each resource unit configuration available.

II. Computerized Implementation

Referring now to FIG. 3, a more detailed diagram of a computerized implementation 100 of the present invention is shown. As depicted, implementation 100 includes computer system 104 deployed within a computer infrastructure 102. This is intended to demonstrate, among other things, that the present invention could be implemented within a network environment (e.g., the Internet, a wide area network (WAN), a local area network (LAN), a virtual private network (VPN), etc.), or on a stand-alone computer system. In the case of the former, communication throughout the network can occur via any combination of various types of communications links. For example, the communication links can comprise addressable connections that may utilize any combination of wired and/or wireless transmission methods. Where communications occur via the Internet, connectivity could be provided by conventional TCP/IP sockets-based protocol, and an Internet service provider could be used to establish connectivity to the Internet. Still yet, computer infrastructure 102 is intended to demonstrate that some or all of the components of implementation 100 could be deployed, managed, serviced, etc. by a service provider who offers to implement, deploy, and/or perform the functions of the present invention for others.

As shown, computer system 104 includes a processing unit 106, a memory 108, a bus 110, and input/output (I/O) interfaces 112. Further, computer system 104 is shown in communication with external I/O devices/resources 114 and storage system 116. In general, processing unit 106 executes computer program code, such as scalability program 118, which is stored in memory 108 and/or storage system 116. While executing computer program code, processing unit 106 can read and/or write data to/from memory 108, storage system 116, and/or I/O interfaces 112. Bus 110 provides a communication link between each of the components in computer system 104. External devices 114 can comprise any devices (e.g., keyboard, pointing device, display, etc.) that enable a user to interact with computer system 104 and/or any devices (e.g., network card, modem, etc.) that enable computer system 104 to communicate with one or more other computing devices.

Computer infrastructure 102 is only illustrative of various types of computer infrastructures for implementing the invention. For example, in one embodiment, computer infrastructure 102 comprises two or more computing devices (e.g., a server cluster) that communicate over a network to perform the process(es) of the invention. Moreover, computer system 104 is only representative of various possible computer systems that can include numerous combinations of hardware. To this extent, in other embodiments, computer system 104 can comprise any specific purpose computing article of manufacture comprising hardware and/or computer program code for performing specific functions, any computing article of manufacture that comprises a combination of specific purpose and general purpose hardware/software, or the like. In each case, the program code and hardware can be created using standard programming and engineering techniques, respectively. Moreover, processing unit 106 may comprise a single processing unit, or be distributed across one or more processing units in one or more locations, e.g., on a client and server. Similarly, memory 108 and/or storage system 116 can comprise any combination of various types of data storage and/or transmission media that reside at one or more physical locations. Further, I/O interfaces 112 can comprise any system for exchanging information with one or more external device 114. Still further, it is understood that one or more additional components (e.g., system software, math co-processing unit, etc.) not shown in FIG. 3 can be included in computer system 104. However, if computer system 104 comprises a handheld device or the like, it is understood that one or more external devices 114 (e.g., a display) and/or storage system 116 could be contained within computer system 104, not externally as shown.

Storage system 116 can be any type of system (e.g., a database) capable of providing storage for information under the present invention. To this extent, storage system 116 could include one or more storage devices, such as a magnetic disk drive or an optical disk drive. In another embodiment, storage system 116 includes data distributed across, for example, a local area network (LAN), wide area network (WAN) or a storage area network (SAN) (not shown). In addition, although not shown, additional components, such as cache memory, communication systems, system software, etc., may be incorporated into computer system 104. It should be understood computer system 104 could be any combination of human, hardware and/or software. It is shown as such to illustrate the functions as described herein. To this extent, the functions of computer system 104 could be provided by any of the components of FIG. 1 (e.g., agents 14A-N, resource unit broker 28 shown separately in FIG. 3 for illustrative purposes).

Shown in memory 108 of computer system 104 is scalability program 118, which facilitates the functions as described herein. It should be understood that resource unit broker 28 can provide any of functions described in the above-incorporated applications. As depicted, scalability program 118 includes input system 120, translation system 122, division system 124, matrix system 126, and output system 128. It should be understood that this configuration of functionality is intended to be illustrative only, and that identical or similar functionality could be provided with a different configuration of systems.

In any event, scalability program 118 facilitates the functions as described herein. Specifically, input system 120 is configured to obtain configuration information, and extract any configuration information pertaining to a scalability service category. Translation system 122 will then translate the configuration information that pertains to a scalability service category into a quantity of resource units. Division system 124 divides the quantity of resource units by an associated cost for each of a set of service levels. Matrix system 126 will determine a maximum quantity of each of the set of service levels that can be allocated for the quantity of resource units, and generate a matrix of possible configurations. Output system 128 will provide the matrix to resource unit broker 28 (in the event that scalability program 118 is not provided directly on resource unit broker 28. In any event, upon receipt of the matrix, resource unit broker 28 will use the matrix in an auction of computer resources, determine a winner of the auction, apply a multiplier to a bid of chips submitted by the winner to yield an adjusted amount of chips, and deducting the adjusted amount of chips from a quantity of chips allocated to the winner. These functions could be provided by an auction program or the like (having one or more subsystems). Such an auction program could incorporate any of the functions of the above-incorporated applications.

While shown and described herein as a method and system for applying brokering characteristics to scalability characteristics, it is understood that the invention further provides various alternative embodiments. For example, in one embodiment, the invention provides a computer-readable/useable medium that includes computer program code to enable a computer infrastructure to apply brokering methods to scalability characteristics. To this extent, the computer-readable/useable medium includes program code that implements the process(es) of the invention. It is understood that the terms computer-readable medium or computer useable medium comprises one or more of any type of physical embodiment of the program code. In particular, the computer-readable/useable medium can comprise program code embodied on one or more portable storage articles of manufacture (e.g., a compact disc, a magnetic disk, a tape, etc.), on one or more data storage portions of a computing device, such as memory 108 (FIG. 3) and/or storage system 116 (FIG. 3) (e.g., a fixed disk, a read-only memory, a random access memory, a cache memory, etc.), and/or as a data signal (e.g., a propagated signal) traveling over a network (e.g., during a wired/wireless electronic distribution of the program code).

In another embodiment, the invention provides a business method that performs the process of the invention on a subscription, advertising, and/or fee basis. That is, a service provider, such as a Solution Integrator, could offer to apply brokering methods to scalability characteristics. In this case, the service provider can create, maintain, support, etc., a computer infrastructure, such as computer infrastructure 102 (FIG. 3) that performs the process of the invention for one or more customers. In return, the service provider can receive payment from the customer(s) under a subscription and/or fee agreement and/or the service provider can receive payment from the sale of advertising content to one or more third parties.

In still another embodiment, the invention provides a computer-implemented method for applying brokering methods to scalability characteristics. In this case, a computer infrastructure, such as computer infrastructure 102 (FIG. 3), can be provided and one or more systems for performing the process of the invention can be obtained (e.g., created, purchased, used, modified, etc.) and deployed to the computer infrastructure. To this extent, the deployment of a system can comprise one or more of: (1) installing program code on a computing device, such as computer system 104 (FIG. 3), from a computer-readable medium; (2) adding one or more computing devices to the computer infrastructure; and (3) incorporating and/or modifying one or more existing systems of the computer infrastructure to enable the computer infrastructure to perform the process of the invention.

As used herein, it is understood that the terms “program code” and “computer program code” are synonymous and mean any expression, in any language, code or notation, of a set of instructions intended to cause a computing device having an information processing capability to perform a particular function either directly or after either or both of the following: (a) conversion to another language, code or notation; and/or (b) reproduction in a different material form. To this extent, program code can be embodied as one or more of: an application/software program, component software/a library of functions, an operating system, a basic I/O system/driver for a particular computing and/or I/O device, and the like.

A data processing system suitable for storing and/or executing program code can be provided hereunder and can include at least one processor communicatively coupled, directly or indirectly, to memory element(s) through a system bus. The memory elements can include, but are not limited to, local memory employed during actual execution of the program code, bulk storage, and cache memories that provide temporary storage of at least some program code in order to reduce the number of times code must be retrieved from bulk storage during execution. Input/output or I/O devices (including, but not limited to, keyboards, displays, pointing devices, etc.) can be coupled to the system either directly or through intervening I/O controllers.

Network adapters also may be coupled to the system to enable the data processing system to become coupled to other data processing systems, remote printers, storage devices, and/or the like, through any combination of intervening private or public networks. Illustrative network adapters include, but are not limited to, modems, cable modems and Ethernet cards.

The foregoing description of various aspects of the invention has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed, and obviously, many modifications and variations are possible. Such modifications and variations that may be apparent to a person skilled in the art are intended to be included within the scope of the invention as defined by the accompanying claims. 

1. A method for applying brokering methods to scalability characteristics, comprising: obtaining configuration information; translating the configuration information that pertains to a scalability service category into a quantity of resource units; dividing the quantity of resource units by an associated cost for each of a set of service levels; determining a maximum quantity of each of the set of service levels that can be allocated for the quantity of resource units; and generating a matrix of possible configurations.
 2. The method of claim 1, further comprising using the matrix in an auction of computer resources.
 3. The method of claim 1, further comprising determining a winner of the auction.
 4. The method of claim 3, further comprising applying a multiplier to a bid of chips submitted by the winner to yield an adjusted amount of chips.
 5. The method of claim 4, further comprising deducting the adjusted amount of chips from a quantity of chips allocated to the winner.
 6. The method of claim 4, the bid being submitted to a resource unit broker by an agent on behalf of a party, and the bid being one a plurality of bids submitted by at least one agent on behalf of a plurality of parties.
 7. The method of claim 6, the matrix being provided to the resource unit broker.
 8. A system for applying brokering methods to scalability characteristics, comprising: a system for obtaining configuration information; a system for translating the configuration information that pertains to a scalability service category into a quantity of resource units; a system for dividing the quantity of resource units by an associated cost for each of a set of service levels; a system for determining a maximum quantity of each of the set of service levels that can be allocated for the quantity of resource units; and a system for generating a matrix of possible configurations.
 9. The system of claim 8, further comprising a system for using the matrix in an auction of computer resources.
 10. The system of claim 8, further comprising a system for determining a winner of the auction.
 11. The system of claim 10, further comprising a system for applying a multiplier to a bid of chips submitted by the winner to yield an adjusted amount of chips.
 12. The system of claim 11, further comprising a system for deducting the adjusted amount of chips from a quantity of chips allocated to the winner.
 13. The system of claim 11, the bid being submitted to a resource unit broker by an agent on behalf of a party, and the bid being one a plurality of bids submitted by at least one agent on behalf of a plurality of parties.
 14. The system of claim 13, the matrix being provided to the resource unit broker.
 15. A program product stored on a computer readable medium for applying brokering methods to scalability characteristics, the computer readable medium comprising program code for causing a computer system to: obtain configuration information; translate the configuration information that pertains to a scalability service category into a quantity of resource units; divide the quantity of resource units by an associated cost for each of a set of service levels; determine a maximum quantity of each of the set of service levels that can be allocated for the quantity of resource units; and generate a matrix of possible configurations.
 16. The program product of claim 15, further comprising program code for using the matrix in an auction of computer resources.
 17. The program product of claim 15, further comprising program code for determining a winner of the auction.
 18. The program product of claim 17, further comprising program code for applying a multiplier to a bid of chips submitted by the winner to yield an adjusted amount of chips.
 19. The program product of claim 18, the computer readable medium further comprising program code for causing the computer system to: deduct the adjusted amount of chips from a quantity of chips allocated to the winner.
 20. The program product of claim 18, the bid being submitted to a resource unit broker by an agent on behalf of a party, and the bid being one a plurality of bids submitted by at least one agent on behalf of a plurality of parties.
 21. The program product of claim 20, the matrix being provided to the resource unit broker.
 22. A method for deploying a system for applying brokering methods to scalability characteristics, comprising: providing a computer infrastructure being operable to: obtain configuration information; translate the configuration information that pertains to an availability service category into a quantity of resource units; divide the quantity of resource units by an associated cost for each of a set of service levels; determine a maximum quantity of each of the set of service levels that can be allocated for the quantity of resource units; and generate a matrix of possible configurations. 